-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat: Add tracing to load
, server actions, and handle
/resolve
#13900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: elliott/init-tracing
Are you sure you want to change the base?
feat: Add tracing to load
, server actions, and handle
/resolve
#13900
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
bf91961
to
b504608
Compare
cc0eef5
to
7f08f16
Compare
b504608
to
74ff497
Compare
74ff497
to
be6f6d2
Compare
7f08f16
to
1472161
Compare
be6f6d2
to
3d9b855
Compare
* @param {any} data | ||
* @param {string} [location_description] | ||
*/ | ||
export function validate_load_response(data, location_description) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moved to shared to reduce duplication
* - `'server'` - Enable tracing only on the server side | ||
* - `'client'` - Enable tracing only on the client side | ||
* @default false | ||
* @since 2.22.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO
4995112
to
7a3909c
Compare
7a3909c
to
3516dd4
Compare
Adds spans to
load
(on the server), server actions, andhandle
/resolve
.We're punting on clientside tracing for now, as we do not feel the o11y community has sufficiently converged on approaches (see https://github.com/open-telemetry/community/blob/main/projects/browser-phase-1.md). When OTEL provides a stable and truly browser-native tracing platform, we'll be all over it.
Want to play around with it?
Clone the repo: https://github.com/elliott-with-the-longest-name-on-github/test-tracing
Set up something like Jaeger (you can copy and run the Docker command at the top of this file to get it up and running with UI and ingestion ports): https://www.jaegertracing.io/docs/2.7/getting-started/
Then build and run your app:
pnpm build && node --import ./instrumentation.server.mjs build/index.js
Visit
localhost:3000/one/two/three/four
, click some buttons to see different scenarios. This will generate traces you can view in Jaeger.TODO:
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits